Dynomotion

Group: DynoMotion Message: 3785 From: bradodarb Date: 2/7/2012
Subject: Double Ksteps
Hello Tom,


I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?

-Brad Murry
Group: DynoMotion Message: 3786 From: Tom Kerekes Date: 2/7/2012
Subject: Re: Double Ksteps
Hi Brad,
 
There is this:
 
 
But now that you mention it it needs a section on using two KSTEPS.
 
The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
 
(8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
 
BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change.  Currently the only way to do that is from C
 
 
FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
 
Regards
TK
 

Group: DynoMotion Message: 3787 From: Brad Murry Date: 2/7/2012
Subject: Re: Double Ksteps

Thanks Tom,

 

I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.

 

Do I only need to set the FPGA command once on INIT?

 

 

-Brad Murry

 

From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
Sent: Tuesday, February 07, 2012 11:52 AM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] Double Ksteps

 

 

Hi Brad,

 

There is this:

 

 

But now that you mention it it needs a section on using two KSTEPS.

 

The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)

The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)

 

(8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).

 

BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change.  Currently the only way to do that is from C

 

 

FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us

 

Regards

TK

 

 

From: bradodarb <bradodarb@...>
To: DynoMotion@yahoogroups.com
Sent: Tuesday, February 7, 2012 10:42 AM
Subject: [DynoMotion] Double Ksteps

 

 

Hello Tom,

I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?

-Brad Murry

 
Group: DynoMotion Message: 3790 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
Hello Tom,


I seem to gave the isolated inputs working right after setting the Global var

KStepPresent=TRUE;

It seems to multiplex fine there.

I cannot seem to get the relay outputs working though...

From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.

Any thoughts?

-Brad Murry



--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> Thanks Tom,
>
>
>
> I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
>
>
>
> Do I only need to set the FPGA command once on INIT?
>
>
>
>
>
> -Brad Murry
>
>
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> Sent: Tuesday, February 07, 2012 11:52 AM
> To: DynoMotion@yahoogroups.com
> Subject: Re: [DynoMotion] Double Ksteps
>
>
>
>
>
> Hi Brad,
>
>
>
> There is this:
>
>
>
> http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
>
>
>
> But now that you mention it it needs a section on using two KSTEPS.
>
>
>
> The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
>
> The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
>
>
>
> (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
>
>
>
> BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
>
>
>
>
>
> FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
>
>
>
> Regards
>
> TK
>
>
>
>
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 10:42 AM
> Subject: [DynoMotion] Double Ksteps
>
>
>
>
>
> Hello Tom,
>
> I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
>
> -Brad Murry
>
Group: DynoMotion Message: 3791 From: Tom Kerekes Date: 2/7/2012
Subject: Re: Double Ksteps
They need to be configured a Outputs.
 
TK

Group: DynoMotion Message: 3792 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
They are....

-Brad

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> They need to be configured a Outputs.
>  
> TK
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 2:10 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>  
> Hello Tom,
>
> I seem to gave the isolated inputs working right after setting the Global var
>
> KStepPresent=TRUE;
>
> It seems to multiplex fine there.
>
> I cannot seem to get the relay outputs working though...
>
> From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
>
> Any thoughts?
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > Thanks Tom,
> >
> >
> >
> > I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
> >
> >
> >
> > Do I only need to set the FPGA command once on INIT?
> >
> >
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> > Sent: Tuesday, February 07, 2012 11:52 AM
> > To: DynoMotion@yahoogroups.com
> > Subject: Re: [DynoMotion] Double Ksteps
> >
> >
> >
> >
> >
> > Hi Brad,
> >
> >
> >
> > There is this:
> >
> >
> >
> > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> >
> >
> >
> > But now that you mention it it needs a section on using two KSTEPS.
> >
> >
> >
> > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> >
> > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> >
> >
> >
> > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> >
> >
> >
> > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> >
> >
> >
> >
> >
> > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> >
> >
> >
> > Regards
> >
> > TK
> >
> >
> >
> >
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, February 7, 2012 10:42 AM
> > Subject: [DynoMotion] Double Ksteps
> >
> >
> >
> >
> >
> > Hello Tom,
> >
> > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> >
> > -Brad Murry
> >
>
Group: DynoMotion Message: 3793 From: Tom Kerekes Date: 2/7/2012
Subject: Re: Double Ksteps
Hi Brad,
 
It was worth a shot :}
 
No ideas.  How are you wiring ?  Testing?
 
They are just a darlington photo transistor that should turn on
 
TK

Group: DynoMotion Message: 3794 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
I am also seeing a lot of state flickering in bits 2-3.

Is there a recommended grounding I should be doing here?

I am only using USB power, should we be using the poer connector?

If so, do we need to provide both 12v and 5v or can we just supply the 5v?


Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?

In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?

Thanks,

Brad Murry

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> They need to be configured a Outputs.
>  
> TK
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 2:10 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>  
> Hello Tom,
>
> I seem to gave the isolated inputs working right after setting the Global var
>
> KStepPresent=TRUE;
>
> It seems to multiplex fine there.
>
> I cannot seem to get the relay outputs working though...
>
> From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
>
> Any thoughts?
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > Thanks Tom,
> >
> >
> >
> > I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
> >
> >
> >
> > Do I only need to set the FPGA command once on INIT?
> >
> >
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> > Sent: Tuesday, February 07, 2012 11:52 AM
> > To: DynoMotion@yahoogroups.com
> > Subject: Re: [DynoMotion] Double Ksteps
> >
> >
> >
> >
> >
> > Hi Brad,
> >
> >
> >
> > There is this:
> >
> >
> >
> > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> >
> >
> >
> > But now that you mention it it needs a section on using two KSTEPS.
> >
> >
> >
> > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> >
> > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> >
> >
> >
> > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> >
> >
> >
> > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> >
> >
> >
> >
> >
> > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> >
> >
> >
> > Regards
> >
> > TK
> >
> >
> >
> >
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, February 7, 2012 10:42 AM
> > Subject: [DynoMotion] Double Ksteps
> >
> >
> >
> >
> >
> > Hello Tom,
> >
> > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> >
> > -Brad Murry
> >
>
Group: DynoMotion Message: 3795 From: Tom Kerekes Date: 2/7/2012
Subject: Re: Double Ksteps
Hi Brad,
 
Flikering on bits 2 and 3 is normal.  Thos are the multiplexing control bits going to KSTEP.
 
USB power should be fine.  In either case +12V is never required.  Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB.  This is convienient for running Motors on +12V using a PC power supply.  But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.
 
No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it.  The current will flow from the + to the - when energized.
 
TK

Group: DynoMotion Message: 3796 From: Brad Murry Date: 2/7/2012
Subject: Re: Double Ksteps

I see…. I misread and thought it was providing access to NO/NC

 

 

Thanks Tom,

 

-Brad

From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
Sent: Tuesday, February 07, 2012 3:31 PM
To: DynoMotion@yahoogroups.com
Subject: Re: [DynoMotion] Re: Double Ksteps

 

 

Hi Brad,

 

Flikering on bits 2 and 3 is normal.  Thos are the multiplexing control bits going to KSTEP.

 

USB power should be fine.  In either case +12V is never required.  Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB.  This is convienient for running Motors on +12V using a PC power supply.  But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.

 

No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it.  The current will flow from the + to the - when energized.

 

TK

 

From: bradodarb <bradodarb@...>
To: DynoMotion@yahoogroups.com
Sent: Tuesday, February 7, 2012 2:20 PM
Subject: [DynoMotion] Re: Double Ksteps

 

 

I am also seeing a lot of state flickering in bits 2-3.

Is there a recommended grounding I should be doing here?

I am only using USB power, should we be using the poer connector?

If so, do we need to provide both 12v and 5v or can we just supply the 5v?

Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?

In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?

Thanks,

Brad Murry

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> They need to be configured a Outputs.
>  
> TK
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 2:10 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>  
> Hello Tom,
>
> I seem to gave the isolated inputs working right after setting the Global var
>
> KStepPresent=TRUE;
>
> It seems to multiplex fine there.
>
> I cannot seem to get the relay outputs working though...
>
> From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
>
> Any thoughts?
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > Thanks Tom,
> >
> >
> >
> > I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
> >
> >
> >
> > Do I only need to set the FPGA command once on INIT?
> >
> >
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> > Sent: Tuesday, February 07, 2012 11:52 AM
> > To: DynoMotion@yahoogroups.com
> > Subject: Re: [DynoMotion] Double Ksteps
> >
> >
> >
> >
> >
> > Hi Brad,
> >
> >
> >
> > There is this:
> >
> >
> >
> > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> >
> >
> >
> > But now that you mention it it needs a section on using two KSTEPS.
> >
> >
> >
> > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> >
> > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> >
> >
> >
> > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> >
> >
> >
> > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> >
> >
> >
> >
> >
> > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> >
> >
> >
> > Regards
> >
> > TK
> >
> >
> >
> >
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, February 7, 2012 10:42 AM
> > Subject: [DynoMotion] Double Ksteps
> >
> >
> >
> >
> >
> > Hello Tom,
> >
> > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> >
> > -Brad Murry
> >
>

 
Group: DynoMotion Message: 3799 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
Hello Tom,

I saw that to 'enable' the Kstep amp::



From C code the Amplifiers may be enabled with the code shown below.



SetBitDirection(45,1); // set Enable Signal as Output

SetBit(45); // Enable the KStep Amplifiers





Will this work for both ksteps?


-Brad Murry

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> I see…. I misread and thought it was providing access to NO/NC
>
>
>
>
>
> Thanks Tom,
>
>
>
> -Brad
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> Sent: Tuesday, February 07, 2012 3:31 PM
> To: DynoMotion@yahoogroups.com
> Subject: Re: [DynoMotion] Re: Double Ksteps
>
>
>
>
>
> Hi Brad,
>
>
>
> Flikering on bits 2 and 3 is normal. Thos are the multiplexing control bits going to KSTEP.
>
>
>
> USB power should be fine. In either case +12V is never required. Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB. This is convienient for running Motors on +12V using a PC power supply. But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.
>
>
>
> No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it. The current will flow from the + to the - when energized.
>
>
>
> TK
>
>
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 2:20 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>
>
>
> I am also seeing a lot of state flickering in bits 2-3.
>
> Is there a recommended grounding I should be doing here?
>
> I am only using USB power, should we be using the poer connector?
>
> If so, do we need to provide both 12v and 5v or can we just supply the 5v?
>
> Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?
>
> In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?
>
> Thanks,
>
> Brad Murry
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> >
> > They need to be configured a Outputs.
> > Â
> > TK
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > Sent: Tuesday, February 7, 2012 2:10 PM
> > Subject: [DynoMotion] Re: Double Ksteps
> >
> >
> > Â
> > Hello Tom,
> >
> > I seem to gave the isolated inputs working right after setting the Global var
> >
> > KStepPresent=TRUE;
> >
> > It seems to multiplex fine there.
> >
> > I cannot seem to get the relay outputs working though...
> >
> > From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
> >
> > Any thoughts?
> >
> > -Brad Murry
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > >
> > > Thanks Tom,
> > >
> > >
> > >
> > > I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
> > >
> > >
> > >
> > > Do I only need to set the FPGA command once on INIT?
> > >
> > >
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of Tom Kerekes
> > > Sent: Tuesday, February 07, 2012 11:52 AM
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Subject: Re: [DynoMotion] Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > Hi Brad,
> > >
> > >
> > >
> > > There is this:
> > >
> > >
> > >
> > > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> > >
> > >
> > >
> > > But now that you mention it it needs a section on using two KSTEPS.
> > >
> > >
> > >
> > > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> > >
> > > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> > >
> > >
> > >
> > > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> > >
> > >
> > >
> > > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> > >
> > >
> > >
> > >
> > >
> > > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> > >
> > >
> > >
> > > Regards
> > >
> > > TK
> > >
> > >
> > >
> > >
> > >
> > > From: bradodarb <bradodarb@>
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Sent: Tuesday, February 7, 2012 10:42 AM
> > > Subject: [DynoMotion] Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > Hello Tom,
> > >
> > > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> > >
> > > -Brad Murry
> > >
> >
>
Group: DynoMotion Message: 3801 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
Hello Tom,

I saw that to 'enable' the Kstep amp::



From C code the Amplifiers may be enabled with the code shown below.



SetBitDirection(45,1); // set Enable Signal as Output

SetBit(45); // Enable the KStep Amplifiers





Will this work for both ksteps?


-Brad Murry

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> I see…. I misread and thought it was providing access to NO/NC
>
>
>
>
>
> Thanks Tom,
>
>
>
> -Brad
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> Sent: Tuesday, February 07, 2012 3:31 PM
> To: DynoMotion@yahoogroups.com
> Subject: Re: [DynoMotion] Re: Double Ksteps
>
>
>
>
>
> Hi Brad,
>
>
>
> Flikering on bits 2 and 3 is normal. Thos are the multiplexing control bits going to KSTEP.
>
>
>
> USB power should be fine. In either case +12V is never required. Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB. This is convienient for running Motors on +12V using a PC power supply. But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.
>
>
>
> No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it. The current will flow from the + to the - when energized.
>
>
>
> TK
>
>
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 2:20 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>
>
>
> I am also seeing a lot of state flickering in bits 2-3.
>
> Is there a recommended grounding I should be doing here?
>
> I am only using USB power, should we be using the poer connector?
>
> If so, do we need to provide both 12v and 5v or can we just supply the 5v?
>
> Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?
>
> In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?
>
> Thanks,
>
> Brad Murry
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> >
> > They need to be configured a Outputs.
> > Â
> > TK
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > Sent: Tuesday, February 7, 2012 2:10 PM
> > Subject: [DynoMotion] Re: Double Ksteps
> >
> >
> > Â
> > Hello Tom,
> >
> > I seem to gave the isolated inputs working right after setting the Global var
> >
> > KStepPresent=TRUE;
> >
> > It seems to multiplex fine there.
> >
> > I cannot seem to get the relay outputs working though...
> >
> > From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
> >
> > Any thoughts?
> >
> > -Brad Murry
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > >
> > > Thanks Tom,
> > >
> > >
> > >
> > > I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
> > >
> > >
> > >
> > > Do I only need to set the FPGA command once on INIT?
> > >
> > >
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of Tom Kerekes
> > > Sent: Tuesday, February 07, 2012 11:52 AM
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Subject: Re: [DynoMotion] Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > Hi Brad,
> > >
> > >
> > >
> > > There is this:
> > >
> > >
> > >
> > > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> > >
> > >
> > >
> > > But now that you mention it it needs a section on using two KSTEPS.
> > >
> > >
> > >
> > > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> > >
> > > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> > >
> > >
> > >
> > > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> > >
> > >
> > >
> > > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> > >
> > >
> > >
> > >
> > >
> > > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> > >
> > >
> > >
> > > Regards
> > >
> > > TK
> > >
> > >
> > >
> > >
> > >
> > > From: bradodarb <bradodarb@>
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Sent: Tuesday, February 7, 2012 10:42 AM
> > > Subject: [DynoMotion] Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > Hello Tom,
> > >
> > > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> > >
> > > -Brad Murry
> > >
> >
>
Group: DynoMotion Message: 3802 From: TK Date: 2/7/2012
Subject: Re: Double Ksteps
Yes jumpering J6 terminals from the first KSTEP to the Second KSTEP will connect the enables together. 

TK

On Feb 7, 2012, at 3:17 PM, "bradodarb" <bradodarb@...> wrote:

 

Hello Tom,

I saw that to 'enable' the Kstep amp::

From C code the Amplifiers may be enabled with the code shown below.

SetBitDirection(45,1); // set Enable Signal as Output

SetBit(45); // Enable the KStep Amplifiers

Will this work for both ksteps?

-Brad Murry

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> I see…. I misread and thought it was providing access to NO/NC
>
>
>
>
>
> Thanks Tom,
>
>
>
> -Brad
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> Sent: Tuesday, February 07, 2012 3:31 PM
> To: DynoMotion@yahoogroups.com
> Subject: Re: [DynoMotion] Re: Double Ksteps
>
>
>
>
>
> Hi Brad,
>
>
>
> Flikering on bits 2 and 3 is normal. Thos are the multiplexing control bits going to KSTEP.
>
>
>
> USB power should be fine. In either case +12V is never required. Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB. This is convienient for running Motors on +12V using a PC power supply. But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.
>
>
>
> No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it. The current will flow from the + to the - when energized.
>
>
>
> TK
>
>
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 2:20 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>
>
>
> I am also seeing a lot of state flickering in bits 2-3.
>
> Is there a recommended grounding I should be doing here?
>
> I am only using USB power, should we be using the poer connector?
>
> If so, do we need to provide both 12v and 5v or can we just supply the 5v?
>
> Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?
>
> In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?
>
> Thanks,
>
> Brad Murry
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> >
> > They need to be configured a Outputs.
> > Â
> > TK
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > Sent: Tuesday, February 7, 2012 2:10 PM
> > Subject: [DynoMotion] Re: Double Ksteps
> >
> >
> > Â
> > Hello Tom,
> >
> > I seem to gave the isolated inputs working right after setting the Global var
> >
> > KStepPresent=TRUE;
> >
> > It seems to multiplex fine there.
> >
> > I cannot seem to get the relay outputs working though...
> >
> > From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
> >
> > Any thoughts?
> >
> > -Brad Murry
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > >
> > > Thanks Tom,
> > >
> > >
> > >
> > > I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
> > >
> > >
> > >
> > > Do I only need to set the FPGA command once on INIT?
> > >
> > >
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of Tom Kerekes
> > > Sent: Tuesday, February 07, 2012 11:52 AM
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Subject: Re: [DynoMotion] Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > Hi Brad,
> > >
> > >
> > >
> > > There is this:
> > >
> > >
> > >
> > > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> > >
> > >
> > >
> > > But now that you mention it it needs a section on using two KSTEPS.
> > >
> > >
> > >
> > > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> > >
> > > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> > >
> > >
> > >
> > > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> > >
> > >
> > >
> > > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> > >
> > >
> > >
> > >
> > >
> > > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> > >
> > >
> > >
> > > Regards
> > >
> > > TK
> > >
> > >
> > >
> > >
> > >
> > > From: bradodarb <bradodarb@>
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Sent: Tuesday, February 7, 2012 10:42 AM
> > > Subject: [DynoMotion] Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > Hello Tom,
> > >
> > > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> > >
> > > -Brad Murry
> > >
> >
>
Group: DynoMotion Message: 3803 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
Hello Tom,

I've got the laser light show working on the outputs, limits are working on the inputs, and mild success in the motor department.

The primary Kstep has all four channels used, and the second Kstep is using J4 and J5.

I modified the InitKStep3axis.c to add in the extra axes, and the output channels are defined as 8,9,10,11,14,15.

I seem to get good motion from channels 0 and 1, noisy jitters from channel 2 and dead nothing from the rest.


Surely I am missing something...

Thank you,

Brad Murry


P.S. - Here is my init code::
#include "KMotionDef.h"

// Defines axis 0, 1, 2 as simple step dir TTL outputs for KSTEP
// enables them
// sets them as an xyz coordinate system for GCode

int main()
{
double T0, LastX=0, LastY=0, LastZ=0, Tau;

KStepPresent=TRUE; // enable KSTEP input multiplexing
FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
ch0->InputMode=NO_INPUT_MODE;
ch0->OutputMode=STEP_DIR_MODE;
ch0->Vel=40000;
ch0->Accel=200000;
ch0->Jerk=4e+006;
ch0->P=0;
ch0->I=0.01;
ch0->D=0;
ch0->FFAccel=0;
ch0->FFVel=0;
ch0->MaxI=200;
ch0->MaxErr=1e+006;
ch0->MaxOutput=200;
ch0->DeadBandGain=1;
ch0->DeadBandRange=0;
ch0->InputChan0=0;
ch0->InputChan1=0;
ch0->OutputChan0=8;
ch0->OutputChan1=0;
ch0->MasterAxis=-1;
ch0->LimitSwitchOptions=0x0;
ch0->InputGain0=1;
ch0->InputGain1=1;
ch0->InputOffset0=0;
ch0->InputOffset1=0;
ch0->OutputGain=1;
ch0->OutputOffset=0;
ch0->SlaveGain=1;
ch0->BacklashMode=BACKLASH_OFF;
ch0->BacklashAmount=0;
ch0->BacklashRate=0;
ch0->invDistPerCycle=1;
ch0->Lead=0;
ch0->MaxFollowingError=1000000000;
ch0->StepperAmplitude=20;

ch0->iir[0].B0=1;
ch0->iir[0].B1=0;
ch0->iir[0].B2=0;
ch0->iir[0].A1=0;
ch0->iir[0].A2=0;

ch0->iir[1].B0=1;
ch0->iir[1].B1=0;
ch0->iir[1].B2=0;
ch0->iir[1].A1=0;
ch0->iir[1].A2=0;

ch0->iir[2].B0=0.000769;
ch0->iir[2].B1=0.001538;
ch0->iir[2].B2=0.000769;
ch0->iir[2].A1=1.92076;
ch0->iir[2].A2=-0.923833;
EnableAxisDest(0,0);

ch1->InputMode=NO_INPUT_MODE;
ch1->OutputMode=STEP_DIR_MODE;
ch1->Vel=40000;
ch1->Accel=200000;
ch1->Jerk=4e+006;
ch1->P=0;
ch1->I=0.01;
ch1->D=0;
ch1->FFAccel=0;
ch1->FFVel=0;
ch1->MaxI=200;
ch1->MaxErr=1e+006;
ch1->MaxOutput=200;
ch1->DeadBandGain=1;
ch1->DeadBandRange=0;
ch1->InputChan0=0;
ch1->InputChan1=0;
ch1->OutputChan0=9;
ch1->OutputChan1=0;
ch1->MasterAxis=-1;
ch1->LimitSwitchOptions=0x0;
ch1->InputGain0=1;
ch1->InputGain1=1;
ch1->InputOffset0=0;
ch1->InputOffset1=0;
ch1->OutputGain=1;
ch1->OutputOffset=0;
ch1->SlaveGain=1;
ch1->BacklashMode=BACKLASH_OFF;
ch1->BacklashAmount=0;
ch1->BacklashRate=0;
ch1->invDistPerCycle=1;
ch1->Lead=0;
ch1->MaxFollowingError=1000000000;
ch1->StepperAmplitude=20;

ch1->iir[0].B0=1;
ch1->iir[0].B1=0;
ch1->iir[0].B2=0;
ch1->iir[0].A1=0;
ch1->iir[0].A2=0;

ch1->iir[1].B0=1;
ch1->iir[1].B1=0;
ch1->iir[1].B2=0;
ch1->iir[1].A1=0;
ch1->iir[1].A2=0;

ch1->iir[2].B0=0.000769;
ch1->iir[2].B1=0.001538;
ch1->iir[2].B2=0.000769;
ch1->iir[2].A1=1.92076;
ch1->iir[2].A2=-0.923833;
EnableAxisDest(1,0);

ch2->InputMode=NO_INPUT_MODE;
ch2->OutputMode=STEP_DIR_MODE;
ch2->Vel=40000;
ch2->Accel=200000;
ch2->Jerk=4e+006;
ch2->P=0;
ch2->I=0.01;
ch2->D=0;
ch2->FFAccel=0;
ch2->FFVel=0;
ch2->MaxI=200;
ch2->MaxErr=1e+006;
ch2->MaxOutput=200;
ch2->DeadBandGain=1;
ch2->DeadBandRange=0;
ch2->InputChan0=0;
ch2->InputChan1=0;
ch2->OutputChan0=10;
ch2->OutputChan1=0;
ch2->MasterAxis=-1;
ch2->LimitSwitchOptions=0x0;
ch2->InputGain0=1;
ch2->InputGain1=1;
ch2->InputOffset0=0;
ch2->InputOffset1=0;
ch2->OutputGain=-1;
ch2->OutputOffset=0;
ch2->SlaveGain=1;
ch2->BacklashMode=BACKLASH_OFF;
ch2->BacklashAmount=0;
ch2->BacklashRate=0;
ch2->invDistPerCycle=1;
ch2->Lead=0;
ch2->MaxFollowingError=1000000000;
ch2->StepperAmplitude=20;

ch2->iir[0].B0=1;
ch2->iir[0].B1=0;
ch2->iir[0].B2=0;
ch2->iir[0].A1=0;
ch2->iir[0].A2=0;

ch2->iir[1].B0=1;
ch2->iir[1].B1=0;
ch2->iir[1].B2=0;
ch2->iir[1].A1=0;
ch2->iir[1].A2=0;

ch2->iir[2].B0=1;
ch2->iir[2].B1=0;
ch2->iir[2].B2=0;
ch2->iir[2].A1=0;
ch2->iir[2].A2=0;
EnableAxisDest(2,0);


ch3->InputMode=NO_INPUT_MODE;
ch3->OutputMode=STEP_DIR_MODE;
ch3->Vel=40000;
ch3->Accel=200000;
ch3->Jerk=4e+006;
ch3->P=0;
ch3->I=0.01;
ch3->D=0;
ch3->FFAccel=0;
ch3->FFVel=0;
ch3->MaxI=200;
ch3->MaxErr=1e+006;
ch3->MaxOutput=200;
ch3->DeadBandGain=1;
ch3->DeadBandRange=0;
ch3->InputChan0=0;
ch3->InputChan1=0;
ch3->OutputChan0=11;
ch3->OutputChan1=0;
ch3->MasterAxis=-1;
ch3->LimitSwitchOptions=0x0;
ch3->InputGain0=1;
ch3->InputGain1=1;
ch3->InputOffset0=0;
ch3->InputOffset1=0;
ch3->OutputGain=-1;
ch3->OutputOffset=0;
ch3->SlaveGain=1;
ch3->BacklashMode=BACKLASH_OFF;
ch3->BacklashAmount=0;
ch3->BacklashRate=0;
ch3->invDistPerCycle=1;
ch3->Lead=0;
ch3->MaxFollowingError=1000000000;
ch3->StepperAmplitude=20;

ch3->iir[0].B0=1;
ch3->iir[0].B1=0;
ch3->iir[0].B2=0;
ch3->iir[0].A1=0;
ch3->iir[0].A2=0;

ch3->iir[1].B0=1;
ch3->iir[1].B1=0;
ch3->iir[1].B2=0;
ch3->iir[1].A1=0;
ch3->iir[1].A2=0;

ch3->iir[2].B0=1;
ch3->iir[2].B1=0;
ch3->iir[2].B2=0;
ch3->iir[2].A1=0;
ch3->iir[2].A2=0;
EnableAxisDest(3,0);



ch4->InputMode=NO_INPUT_MODE;
ch4->OutputMode=STEP_DIR_MODE;
ch4->Vel=40000;
ch4->Accel=200000;
ch4->Jerk=4e+006;
ch4->P=0;
ch4->I=0.01;
ch4->D=0;
ch4->FFAccel=0;
ch4->FFVel=0;
ch4->MaxI=200;
ch4->MaxErr=1e+006;
ch4->MaxOutput=200;
ch4->DeadBandGain=1;
ch4->DeadBandRange=0;
ch4->InputChan0=0;
ch4->InputChan1=0;
ch4->OutputChan0=14;
ch4->OutputChan1=0;
ch4->MasterAxis=-1;
ch4->LimitSwitchOptions=0x0;
ch4->InputGain0=1;
ch4->InputGain1=1;
ch4->InputOffset0=0;
ch4->InputOffset1=0;
ch4->OutputGain=-1;
ch4->OutputOffset=0;
ch4->SlaveGain=1;
ch4->BacklashMode=BACKLASH_OFF;
ch4->BacklashAmount=0;
ch4->BacklashRate=0;
ch4->invDistPerCycle=1;
ch4->Lead=0;
ch4->MaxFollowingError=1000000000;
ch4->StepperAmplitude=20;

ch4->iir[0].B0=1;
ch4->iir[0].B1=0;
ch4->iir[0].B2=0;
ch4->iir[0].A1=0;
ch4->iir[0].A2=0;

ch4->iir[1].B0=1;
ch4->iir[1].B1=0;
ch4->iir[1].B2=0;
ch4->iir[1].A1=0;
ch4->iir[1].A2=0;

ch4->iir[2].B0=1;
ch4->iir[2].B1=0;
ch4->iir[2].B2=0;
ch4->iir[2].A1=0;
ch4->iir[2].A2=0;
EnableAxisDest(4,0);



ch5->InputMode=NO_INPUT_MODE;
ch5->OutputMode=STEP_DIR_MODE;
ch5->Vel=40000;
ch5->Accel=200000;
ch5->Jerk=4e+006;
ch5->P=0;
ch5->I=0.01;
ch5->D=0;
ch5->FFAccel=0;
ch5->FFVel=0;
ch5->MaxI=200;
ch5->MaxErr=1e+006;
ch5->MaxOutput=200;
ch5->DeadBandGain=1;
ch5->DeadBandRange=0;
ch5->InputChan0=0;
ch5->InputChan1=0;
ch5->OutputChan0=15;
ch5->OutputChan1=0;
ch5->MasterAxis=-1;
ch5->LimitSwitchOptions=0x0;
ch5->InputGain0=1;
ch5->InputGain1=1;
ch5->InputOffset0=0;
ch5->InputOffset1=0;
ch5->OutputGain=-1;
ch5->OutputOffset=0;
ch5->SlaveGain=1;
ch5->BacklashMode=BACKLASH_OFF;
ch5->BacklashAmount=0;
ch5->BacklashRate=0;
ch5->invDistPerCycle=1;
ch5->Lead=0;
ch5->MaxFollowingError=1000000000;
ch5->StepperAmplitude=20;

ch5->iir[0].B0=1;
ch5->iir[0].B1=0;
ch3->iir[0].B2=0;
ch5->iir[0].A1=0;
ch5->iir[0].A2=0;

ch5->iir[1].B0=1;
ch5->iir[1].B1=0;
ch5->iir[1].B2=0;
ch5->iir[1].A1=0;
ch5->iir[1].A2=0;

ch5->iir[2].B0=1;
ch5->iir[2].B1=0;
ch5->iir[2].B2=0;
ch5->iir[2].A1=0;
ch5->iir[2].A2=0;
EnableAxisDest(5,0);


DefineCoordSystem6(0,1,2,3,4,5);

SetBitDirection(45,1); // set Enable Signal as Output
SetBit(45); // Enable the amplifiers

// Add a small amount of Coordinated Motion Path smoothing if desired
// Tau = 0.001; // seconds for Low Pass Filter Time Constant
// KLP = exp(-TIMEBASE/Tau);
KLP=0; // force to 0 to disable
// printf("Tau=%f KLP=%f\n",Tau,KLP);


for (;;) // loop forever
{
WaitNextTimeSlice();

// Service Amplifier disable after no activity for a while
if (ch0->Dest != LastX || ch1->Dest != LastY || ch2->Dest != LastZ)
{
// we moved - enable KStep Amplifers
SetBit(45);
T0 = Time_sec(); // record the time and position of last motion
LastX=ch0->Dest;
LastY=ch1->Dest;
LastZ=ch2->Dest;
}
else
{
if (Time_sec() > T0 + 10.0) ClearBit(45);
}
}

return 0;
}



--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
> Hello Tom,
>
> I saw that to 'enable' the Kstep amp::
>
>
>
> From C code the Amplifiers may be enabled with the code shown below.
>
>
>
> SetBitDirection(45,1); // set Enable Signal as Output
>
> SetBit(45); // Enable the KStep Amplifiers
>
>
>
>
>
> Will this work for both ksteps?
>
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > I see…. I misread and thought it was providing access to NO/NC
> >
> >
> >
> >
> >
> > Thanks Tom,
> >
> >
> >
> > -Brad
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> > Sent: Tuesday, February 07, 2012 3:31 PM
> > To: DynoMotion@yahoogroups.com
> > Subject: Re: [DynoMotion] Re: Double Ksteps
> >
> >
> >
> >
> >
> > Hi Brad,
> >
> >
> >
> > Flikering on bits 2 and 3 is normal. Thos are the multiplexing control bits going to KSTEP.
> >
> >
> >
> > USB power should be fine. In either case +12V is never required. Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB. This is convienient for running Motors on +12V using a PC power supply. But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.
> >
> >
> >
> > No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it. The current will flow from the + to the - when energized.
> >
> >
> >
> > TK
> >
> >
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, February 7, 2012 2:20 PM
> > Subject: [DynoMotion] Re: Double Ksteps
> >
> >
> >
> >
> >
> > I am also seeing a lot of state flickering in bits 2-3.
> >
> > Is there a recommended grounding I should be doing here?
> >
> > I am only using USB power, should we be using the poer connector?
> >
> > If so, do we need to provide both 12v and 5v or can we just supply the 5v?
> >
> > Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?
> >
> > In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?
> >
> > Thanks,
> >
> > Brad Murry
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > >
> > > They need to be configured a Outputs.
> > > Â
> > > TK
> > >
> > > From: bradodarb <bradodarb@>
> > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > Sent: Tuesday, February 7, 2012 2:10 PM
> > > Subject: [DynoMotion] Re: Double Ksteps
> > >
> > >
> > > Â
> > > Hello Tom,
> > >
> > > I seem to gave the isolated inputs working right after setting the Global var
> > >
> > > KStepPresent=TRUE;
> > >
> > > It seems to multiplex fine there.
> > >
> > > I cannot seem to get the relay outputs working though...
> > >
> > > From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
> > >
> > > Any thoughts?
> > >
> > > -Brad Murry
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > >
> > > > Thanks Tom,
> > > >
> > > >
> > > >
> > > > I did see some mention here and there about using two cards regarding IO, etc… but was not sure if there were any other caveats.
> > > >
> > > >
> > > >
> > > > Do I only need to set the FPGA command once on INIT?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -Brad Murry
> > > >
> > > >
> > > >
> > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of Tom Kerekes
> > > > Sent: Tuesday, February 07, 2012 11:52 AM
> > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > Subject: Re: [DynoMotion] Double Ksteps
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi Brad,
> > > >
> > > >
> > > >
> > > > There is this:
> > > >
> > > >
> > > >
> > > > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> > > >
> > > >
> > > >
> > > > But now that you mention it it needs a section on using two KSTEPS.
> > > >
> > > >
> > > >
> > > > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> > > >
> > > > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> > > >
> > > >
> > > >
> > > > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> > > >
> > > >
> > > >
> > > > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> > > >
> > > >
> > > >
> > > > Regards
> > > >
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: bradodarb <bradodarb@>
> > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > Sent: Tuesday, February 7, 2012 10:42 AM
> > > > Subject: [DynoMotion] Double Ksteps
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hello Tom,
> > > >
> > > > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> > > >
> > > > -Brad Murry
> > > >
> > >
> >
>
Group: DynoMotion Message: 3804 From: Tom Kerekes Date: 2/7/2012
Subject: Re: Double Ksteps
Hi Brad,
 
That InitKStep3axis.c has an idle loop at the end that will disable everything if none of the first 3 are moving for a while.   So that might be why the other 3 don't move.  Either defeat the idle loop or include a test for any of your 6 axes.
 
You should have all 3 LEDS on both KSTEPS (Motor Power, Enable, +5V)
 
The Jittery motor might be bad motor wiring like only one coil connected.
 
Regards
TK

Group: DynoMotion Message: 3805 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
Hello Tom,

That pretty much worked... did not even notice that loop.

Everything works except #2 is still jittery. The odd thing is channel 7 needs to be diabled as well as 2 for that motor.

-Brad Murry

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Brad,
>  
> That InitKStep3axis.c has an idle loop at the end that will disable everything if none of the first 3 are moving for a while.   So that might be why the other 3 don't move.  Either defeat the idle loop or include a test for any of your 6 axes.
>  
> You should have all 3 LEDS on both KSTEPS (Motor Power, Enable, +5V)
>  
> The Jittery motor might be bad motor wiring like only one coil connected.
>  
> Regards
> TK
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 3:42 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>  
> Hello Tom,
>
> I've got the laser light show working on the outputs, limits are working on the inputs, and mild success in the motor department.
>
> The primary Kstep has all four channels used, and the second Kstep is using J4 and J5.
>
> I modified the InitKStep3axis.c to add in the extra axes, and the output channels are defined as 8,9,10,11,14,15.
>
> I seem to get good motion from channels 0 and 1, noisy jitters from channel 2 and dead nothing from the rest.
>
> Surely I am missing something...
>
> Thank you,
>
> Brad Murry
>
> P.S. - Here is my init code::
> #include "KMotionDef.h"
>
> // Defines axis 0, 1, 2 as simple step dir TTL outputs for KSTEP
> // enables them
> // sets them as an xyz coordinate system for GCode
>
> int main()
> {
> double T0, LastX=0, LastY=0, LastZ=0, Tau;
>
> KStepPresent=TRUE; // enable KSTEP input multiplexing
> FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> ch0->InputMode=NO_INPUT_MODE;
> ch0->OutputMode=STEP_DIR_MODE;
> ch0->Vel=40000;
> ch0->Accel=200000;
> ch0->Jerk=4e+006;
> ch0->P=0;
> ch0->I=0.01;
> ch0->D=0;
> ch0->FFAccel=0;
> ch0->FFVel=0;
> ch0->MaxI=200;
> ch0->MaxErr=1e+006;
> ch0->MaxOutput=200;
> ch0->DeadBandGain=1;
> ch0->DeadBandRange=0;
> ch0->InputChan0=0;
> ch0->InputChan1=0;
> ch0->OutputChan0=8;
> ch0->OutputChan1=0;
> ch0->MasterAxis=-1;
> ch0->LimitSwitchOptions=0x0;
> ch0->InputGain0=1;
> ch0->InputGain1=1;
> ch0->InputOffset0=0;
> ch0->InputOffset1=0;
> ch0->OutputGain=1;
> ch0->OutputOffset=0;
> ch0->SlaveGain=1;
> ch0->BacklashMode=BACKLASH_OFF;
> ch0->BacklashAmount=0;
> ch0->BacklashRate=0;
> ch0->invDistPerCycle=1;
> ch0->Lead=0;
> ch0->MaxFollowingError=1000000000;
> ch0->StepperAmplitude=20;
>
> ch0->iir[0].B0=1;
> ch0->iir[0].B1=0;
> ch0->iir[0].B2=0;
> ch0->iir[0].A1=0;
> ch0->iir[0].A2=0;
>
> ch0->iir[1].B0=1;
> ch0->iir[1].B1=0;
> ch0->iir[1].B2=0;
> ch0->iir[1].A1=0;
> ch0->iir[1].A2=0;
>
> ch0->iir[2].B0=0.000769;
> ch0->iir[2].B1=0.001538;
> ch0->iir[2].B2=0.000769;
> ch0->iir[2].A1=1.92076;
> ch0->iir[2].A2=-0.923833;
> EnableAxisDest(0,0);
>
> ch1->InputMode=NO_INPUT_MODE;
> ch1->OutputMode=STEP_DIR_MODE;
> ch1->Vel=40000;
> ch1->Accel=200000;
> ch1->Jerk=4e+006;
> ch1->P=0;
> ch1->I=0.01;
> ch1->D=0;
> ch1->FFAccel=0;
> ch1->FFVel=0;
> ch1->MaxI=200;
> ch1->MaxErr=1e+006;
> ch1->MaxOutput=200;
> ch1->DeadBandGain=1;
> ch1->DeadBandRange=0;
> ch1->InputChan0=0;
> ch1->InputChan1=0;
> ch1->OutputChan0=9;
> ch1->OutputChan1=0;
> ch1->MasterAxis=-1;
> ch1->LimitSwitchOptions=0x0;
> ch1->InputGain0=1;
> ch1->InputGain1=1;
> ch1->InputOffset0=0;
> ch1->InputOffset1=0;
> ch1->OutputGain=1;
> ch1->OutputOffset=0;
> ch1->SlaveGain=1;
> ch1->BacklashMode=BACKLASH_OFF;
> ch1->BacklashAmount=0;
> ch1->BacklashRate=0;
> ch1->invDistPerCycle=1;
> ch1->Lead=0;
> ch1->MaxFollowingError=1000000000;
> ch1->StepperAmplitude=20;
>
> ch1->iir[0].B0=1;
> ch1->iir[0].B1=0;
> ch1->iir[0].B2=0;
> ch1->iir[0].A1=0;
> ch1->iir[0].A2=0;
>
> ch1->iir[1].B0=1;
> ch1->iir[1].B1=0;
> ch1->iir[1].B2=0;
> ch1->iir[1].A1=0;
> ch1->iir[1].A2=0;
>
> ch1->iir[2].B0=0.000769;
> ch1->iir[2].B1=0.001538;
> ch1->iir[2].B2=0.000769;
> ch1->iir[2].A1=1.92076;
> ch1->iir[2].A2=-0.923833;
> EnableAxisDest(1,0);
>
> ch2->InputMode=NO_INPUT_MODE;
> ch2->OutputMode=STEP_DIR_MODE;
> ch2->Vel=40000;
> ch2->Accel=200000;
> ch2->Jerk=4e+006;
> ch2->P=0;
> ch2->I=0.01;
> ch2->D=0;
> ch2->FFAccel=0;
> ch2->FFVel=0;
> ch2->MaxI=200;
> ch2->MaxErr=1e+006;
> ch2->MaxOutput=200;
> ch2->DeadBandGain=1;
> ch2->DeadBandRange=0;
> ch2->InputChan0=0;
> ch2->InputChan1=0;
> ch2->OutputChan0=10;
> ch2->OutputChan1=0;
> ch2->MasterAxis=-1;
> ch2->LimitSwitchOptions=0x0;
> ch2->InputGain0=1;
> ch2->InputGain1=1;
> ch2->InputOffset0=0;
> ch2->InputOffset1=0;
> ch2->OutputGain=-1;
> ch2->OutputOffset=0;
> ch2->SlaveGain=1;
> ch2->BacklashMode=BACKLASH_OFF;
> ch2->BacklashAmount=0;
> ch2->BacklashRate=0;
> ch2->invDistPerCycle=1;
> ch2->Lead=0;
> ch2->MaxFollowingError=1000000000;
> ch2->StepperAmplitude=20;
>
> ch2->iir[0].B0=1;
> ch2->iir[0].B1=0;
> ch2->iir[0].B2=0;
> ch2->iir[0].A1=0;
> ch2->iir[0].A2=0;
>
> ch2->iir[1].B0=1;
> ch2->iir[1].B1=0;
> ch2->iir[1].B2=0;
> ch2->iir[1].A1=0;
> ch2->iir[1].A2=0;
>
> ch2->iir[2].B0=1;
> ch2->iir[2].B1=0;
> ch2->iir[2].B2=0;
> ch2->iir[2].A1=0;
> ch2->iir[2].A2=0;
> EnableAxisDest(2,0);
>
> ch3->InputMode=NO_INPUT_MODE;
> ch3->OutputMode=STEP_DIR_MODE;
> ch3->Vel=40000;
> ch3->Accel=200000;
> ch3->Jerk=4e+006;
> ch3->P=0;
> ch3->I=0.01;
> ch3->D=0;
> ch3->FFAccel=0;
> ch3->FFVel=0;
> ch3->MaxI=200;
> ch3->MaxErr=1e+006;
> ch3->MaxOutput=200;
> ch3->DeadBandGain=1;
> ch3->DeadBandRange=0;
> ch3->InputChan0=0;
> ch3->InputChan1=0;
> ch3->OutputChan0=11;
> ch3->OutputChan1=0;
> ch3->MasterAxis=-1;
> ch3->LimitSwitchOptions=0x0;
> ch3->InputGain0=1;
> ch3->InputGain1=1;
> ch3->InputOffset0=0;
> ch3->InputOffset1=0;
> ch3->OutputGain=-1;
> ch3->OutputOffset=0;
> ch3->SlaveGain=1;
> ch3->BacklashMode=BACKLASH_OFF;
> ch3->BacklashAmount=0;
> ch3->BacklashRate=0;
> ch3->invDistPerCycle=1;
> ch3->Lead=0;
> ch3->MaxFollowingError=1000000000;
> ch3->StepperAmplitude=20;
>
> ch3->iir[0].B0=1;
> ch3->iir[0].B1=0;
> ch3->iir[0].B2=0;
> ch3->iir[0].A1=0;
> ch3->iir[0].A2=0;
>
> ch3->iir[1].B0=1;
> ch3->iir[1].B1=0;
> ch3->iir[1].B2=0;
> ch3->iir[1].A1=0;
> ch3->iir[1].A2=0;
>
> ch3->iir[2].B0=1;
> ch3->iir[2].B1=0;
> ch3->iir[2].B2=0;
> ch3->iir[2].A1=0;
> ch3->iir[2].A2=0;
> EnableAxisDest(3,0);
>
>
>
> ch4->InputMode=NO_INPUT_MODE;
> ch4->OutputMode=STEP_DIR_MODE;
> ch4->Vel=40000;
> ch4->Accel=200000;
> ch4->Jerk=4e+006;
> ch4->P=0;
> ch4->I=0.01;
> ch4->D=0;
> ch4->FFAccel=0;
> ch4->FFVel=0;
> ch4->MaxI=200;
> ch4->MaxErr=1e+006;
> ch4->MaxOutput=200;
> ch4->DeadBandGain=1;
> ch4->DeadBandRange=0;
> ch4->InputChan0=0;
> ch4->InputChan1=0;
> ch4->OutputChan0=14;
> ch4->OutputChan1=0;
> ch4->MasterAxis=-1;
> ch4->LimitSwitchOptions=0x0;
> ch4->InputGain0=1;
> ch4->InputGain1=1;
> ch4->InputOffset0=0;
> ch4->InputOffset1=0;
> ch4->OutputGain=-1;
> ch4->OutputOffset=0;
> ch4->SlaveGain=1;
> ch4->BacklashMode=BACKLASH_OFF;
> ch4->BacklashAmount=0;
> ch4->BacklashRate=0;
> ch4->invDistPerCycle=1;
> ch4->Lead=0;
> ch4->MaxFollowingError=1000000000;
> ch4->StepperAmplitude=20;
>
> ch4->iir[0].B0=1;
> ch4->iir[0].B1=0;
> ch4->iir[0].B2=0;
> ch4->iir[0].A1=0;
> ch4->iir[0].A2=0;
>
> ch4->iir[1].B0=1;
> ch4->iir[1].B1=0;
> ch4->iir[1].B2=0;
> ch4->iir[1].A1=0;
> ch4->iir[1].A2=0;
>
> ch4->iir[2].B0=1;
> ch4->iir[2].B1=0;
> ch4->iir[2].B2=0;
> ch4->iir[2].A1=0;
> ch4->iir[2].A2=0;
> EnableAxisDest(4,0);
>
>
>
> ch5->InputMode=NO_INPUT_MODE;
> ch5->OutputMode=STEP_DIR_MODE;
> ch5->Vel=40000;
> ch5->Accel=200000;
> ch5->Jerk=4e+006;
> ch5->P=0;
> ch5->I=0.01;
> ch5->D=0;
> ch5->FFAccel=0;
> ch5->FFVel=0;
> ch5->MaxI=200;
> ch5->MaxErr=1e+006;
> ch5->MaxOutput=200;
> ch5->DeadBandGain=1;
> ch5->DeadBandRange=0;
> ch5->InputChan0=0;
> ch5->InputChan1=0;
> ch5->OutputChan0=15;
> ch5->OutputChan1=0;
> ch5->MasterAxis=-1;
> ch5->LimitSwitchOptions=0x0;
> ch5->InputGain0=1;
> ch5->InputGain1=1;
> ch5->InputOffset0=0;
> ch5->InputOffset1=0;
> ch5->OutputGain=-1;
> ch5->OutputOffset=0;
> ch5->SlaveGain=1;
> ch5->BacklashMode=BACKLASH_OFF;
> ch5->BacklashAmount=0;
> ch5->BacklashRate=0;
> ch5->invDistPerCycle=1;
> ch5->Lead=0;
> ch5->MaxFollowingError=1000000000;
> ch5->StepperAmplitude=20;
>
> ch5->iir[0].B0=1;
> ch5->iir[0].B1=0;
> ch3->iir[0].B2=0;
> ch5->iir[0].A1=0;
> ch5->iir[0].A2=0;
>
> ch5->iir[1].B0=1;
> ch5->iir[1].B1=0;
> ch5->iir[1].B2=0;
> ch5->iir[1].A1=0;
> ch5->iir[1].A2=0;
>
> ch5->iir[2].B0=1;
> ch5->iir[2].B1=0;
> ch5->iir[2].B2=0;
> ch5->iir[2].A1=0;
> ch5->iir[2].A2=0;
> EnableAxisDest(5,0);
>
>
> DefineCoordSystem6(0,1,2,3,4,5);
>
> SetBitDirection(45,1); // set Enable Signal as Output
> SetBit(45); // Enable the amplifiers
>
> // Add a small amount of Coordinated Motion Path smoothing if desired
> // Tau = 0.001; // seconds for Low Pass Filter Time Constant
> // KLP = exp(-TIMEBASE/Tau);
> KLP=0; // force to 0 to disable
> // printf("Tau=%f KLP=%f\n",Tau,KLP);
>
>
> for (;;) // loop forever
> {
> WaitNextTimeSlice();
>
> // Service Amplifier disable after no activity for a while
> if (ch0->Dest != LastX || ch1->Dest != LastY || ch2->Dest != LastZ)
> {
> // we moved - enable KStep Amplifers
> SetBit(45);
> T0 = Time_sec(); // record the time and position of last motion
> LastX=ch0->Dest;
> LastY=ch1->Dest;
> LastZ=ch2->Dest;
> }
> else
> {
> if (Time_sec() > T0 + 10.0) ClearBit(45);
> }
> }
>
> return 0;
> }
>
> --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> > Hello Tom,
> >
> > I saw that to 'enable' the Kstep amp::
> >
> >
> >
> > From C code the Amplifiers may be enabled with the code shown below.
> >
> >
> >
> > SetBitDirection(45,1); // set Enable Signal as Output
> >
> > SetBit(45); // Enable the KStep Amplifiers
> >
> >
> >
> >
> >
> > Will this work for both ksteps?
> >
> >
> > -Brad Murry
> >
> > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > >
> > > I see…. I misread and thought it was providing access to NO/NC
> > >
> > >
> > >
> > >
> > >
> > > Thanks Tom,
> > >
> > >
> > >
> > > -Brad
> > >
> > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> > > Sent: Tuesday, February 07, 2012 3:31 PM
> > > To: DynoMotion@yahoogroups.com
> > > Subject: Re: [DynoMotion] Re: Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > Hi Brad,
> > >
> > >
> > >
> > > Flikering on bits 2 and 3 is normal. Thos are the multiplexing control bits going to KSTEP.
> > >
> > >
> > >
> > > USB power should be fine. In either case +12V is never required. Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB. This is convienient for running Motors on +12V using a PC power supply. But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.
> > >
> > >
> > >
> > > No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it. The current will flow from the + to the - when energized.
> > >
> > >
> > >
> > > TK
> > >
> > >
> > >
> > > From: bradodarb <bradodarb@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Tuesday, February 7, 2012 2:20 PM
> > > Subject: [DynoMotion] Re: Double Ksteps
> > >
> > >
> > >
> > >
> > >
> > > I am also seeing a lot of state flickering in bits 2-3.
> > >
> > > Is there a recommended grounding I should be doing here?
> > >
> > > I am only using USB power, should we be using the poer connector?
> > >
> > > If so, do we need to provide both 12v and 5v or can we just supply the 5v?
> > >
> > > Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?
> > >
> > > In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?
> > >
> > > Thanks,
> > >
> > > Brad Murry
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > >
> > > > They need to be configured a Outputs.
> > > > Â
> > > > TK
> > > >
> > > > From: bradodarb <bradodarb@>
> > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > Sent: Tuesday, February 7, 2012 2:10 PM
> > > > Subject: [DynoMotion] Re: Double Ksteps
> > > >
> > > >
> > > > Â
> > > > Hello Tom,
> > > >
> > > > I seem to gave the isolated inputs working right after setting the Global var
> > > >
> > > > KStepPresent=TRUE;
> > > >
> > > > It seems to multiplex fine there.
> > > >
> > > > I cannot seem to get the relay outputs working though...
> > > >
> > > > From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
> > > >
> > > > Any thoughts?
> > > >
> > > > -Brad Murry
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > >
> > > > > Thanks Tom,
> > > > >
> > > > >
> > > > >
> > > > > I did see some mention here and there about using two cards regarding IO, etcÃÆ'¢â‚¬Â¦ but was not sure if there were any other caveats.
> > > > >
> > > > >
> > > > >
> > > > > Do I only need to set the FPGA command once on INIT?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > >
> > > > >
> > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of Tom Kerekes
> > > > > Sent: Tuesday, February 07, 2012 11:52 AM
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > Subject: Re: [DynoMotion] Double Ksteps
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi Brad,
> > > > >
> > > > >
> > > > >
> > > > > There is this:
> > > > >
> > > > >
> > > > >
> > > > > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> > > > >
> > > > >
> > > > >
> > > > > But now that you mention it it needs a section on using two KSTEPS.
> > > > >
> > > > >
> > > > >
> > > > > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> > > > >
> > > > > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> > > > >
> > > > >
> > > > >
> > > > > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> > > > >
> > > > >
> > > > >
> > > > > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> > > > >
> > > > >
> > > > >
> > > > > Regards
> > > > >
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: bradodarb <bradodarb@>
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > Sent: Tuesday, February 7, 2012 10:42 AM
> > > > > Subject: [DynoMotion] Double Ksteps
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hello Tom,
> > > > >
> > > > > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> > > > >
> > > > > -Brad Murry
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 3806 From: Tom Kerekes Date: 2/7/2012
Subject: Re: Double Ksteps
Huh?

Group: DynoMotion Message: 3807 From: bradodarb Date: 2/7/2012
Subject: Re: Double Ksteps
What I meant was channel 2 did not disable when I unchecked enable for channel 2, but did when I unchecked 7 as well.

Anyhow, apparently the observations of jitter were not true, once I specified larger moves the tech said they all look the same.

Now on to homing...

Thanks,

-Brad Murry


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Huh?
>
>
> From: bradodarb <bradodarb@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, February 7, 2012 4:38 PM
> Subject: [DynoMotion] Re: Double Ksteps
>
>
>  
> Hello Tom,
>
> That pretty much worked... did not even notice that loop.
>
> Everything works except #2 is still jittery. The odd thing is channel 7 needs to be diabled as well as 2 for that motor.
>
> -Brad Murry
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Brad,
> >  
> > That InitKStep3axis.c has an idle loop at the end that will disable everything if none of the first 3 are moving for a while.   So that might be why the other 3 don't move.  Either defeat the idle loop or include a test for any of your 6 axes.
> >  
> > You should have all 3 LEDS on both KSTEPS (Motor Power, Enable, +5V)
> >  
> > The Jittery motor might be bad motor wiring like only one coil connected.
> >  
> > Regards
> > TK
> >
> > From: bradodarb <bradodarb@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, February 7, 2012 3:42 PM
> > Subject: [DynoMotion] Re: Double Ksteps
> >
> >
> >  
> > Hello Tom,
> >
> > I've got the laser light show working on the outputs, limits are working on the inputs, and mild success in the motor department.
> >
> > The primary Kstep has all four channels used, and the second Kstep is using J4 and J5.
> >
> > I modified the InitKStep3axis.c to add in the extra axes, and the output channels are defined as 8,9,10,11,14,15.
> >
> > I seem to get good motion from channels 0 and 1, noisy jitters from channel 2 and dead nothing from the rest.
> >
> > Surely I am missing something...
> >
> > Thank you,
> >
> > Brad Murry
> >
> > P.S. - Here is my init code::
> > #include "KMotionDef.h"
> >
> > // Defines axis 0, 1, 2 as simple step dir TTL outputs for KSTEP
> > // enables them
> > // sets them as an xyz coordinate system for GCode
> >
> > int main()
> > {
> > double T0, LastX=0, LastY=0, LastZ=0, Tau;
> >
> > KStepPresent=TRUE; // enable KSTEP input multiplexing
> > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> > ch0->InputMode=NO_INPUT_MODE;
> > ch0->OutputMode=STEP_DIR_MODE;
> > ch0->Vel=40000;
> > ch0->Accel=200000;
> > ch0->Jerk=4e+006;
> > ch0->P=0;
> > ch0->I=0.01;
> > ch0->D=0;
> > ch0->FFAccel=0;
> > ch0->FFVel=0;
> > ch0->MaxI=200;
> > ch0->MaxErr=1e+006;
> > ch0->MaxOutput=200;
> > ch0->DeadBandGain=1;
> > ch0->DeadBandRange=0;
> > ch0->InputChan0=0;
> > ch0->InputChan1=0;
> > ch0->OutputChan0=8;
> > ch0->OutputChan1=0;
> > ch0->MasterAxis=-1;
> > ch0->LimitSwitchOptions=0x0;
> > ch0->InputGain0=1;
> > ch0->InputGain1=1;
> > ch0->InputOffset0=0;
> > ch0->InputOffset1=0;
> > ch0->OutputGain=1;
> > ch0->OutputOffset=0;
> > ch0->SlaveGain=1;
> > ch0->BacklashMode=BACKLASH_OFF;
> > ch0->BacklashAmount=0;
> > ch0->BacklashRate=0;
> > ch0->invDistPerCycle=1;
> > ch0->Lead=0;
> > ch0->MaxFollowingError=1000000000;
> > ch0->StepperAmplitude=20;
> >
> > ch0->iir[0].B0=1;
> > ch0->iir[0].B1=0;
> > ch0->iir[0].B2=0;
> > ch0->iir[0].A1=0;
> > ch0->iir[0].A2=0;
> >
> > ch0->iir[1].B0=1;
> > ch0->iir[1].B1=0;
> > ch0->iir[1].B2=0;
> > ch0->iir[1].A1=0;
> > ch0->iir[1].A2=0;
> >
> > ch0->iir[2].B0=0.000769;
> > ch0->iir[2].B1=0.001538;
> > ch0->iir[2].B2=0.000769;
> > ch0->iir[2].A1=1.92076;
> > ch0->iir[2].A2=-0.923833;
> > EnableAxisDest(0,0);
> >
> > ch1->InputMode=NO_INPUT_MODE;
> > ch1->OutputMode=STEP_DIR_MODE;
> > ch1->Vel=40000;
> > ch1->Accel=200000;
> > ch1->Jerk=4e+006;
> > ch1->P=0;
> > ch1->I=0.01;
> > ch1->D=0;
> > ch1->FFAccel=0;
> > ch1->FFVel=0;
> > ch1->MaxI=200;
> > ch1->MaxErr=1e+006;
> > ch1->MaxOutput=200;
> > ch1->DeadBandGain=1;
> > ch1->DeadBandRange=0;
> > ch1->InputChan0=0;
> > ch1->InputChan1=0;
> > ch1->OutputChan0=9;
> > ch1->OutputChan1=0;
> > ch1->MasterAxis=-1;
> > ch1->LimitSwitchOptions=0x0;
> > ch1->InputGain0=1;
> > ch1->InputGain1=1;
> > ch1->InputOffset0=0;
> > ch1->InputOffset1=0;
> > ch1->OutputGain=1;
> > ch1->OutputOffset=0;
> > ch1->SlaveGain=1;
> > ch1->BacklashMode=BACKLASH_OFF;
> > ch1->BacklashAmount=0;
> > ch1->BacklashRate=0;
> > ch1->invDistPerCycle=1;
> > ch1->Lead=0;
> > ch1->MaxFollowingError=1000000000;
> > ch1->StepperAmplitude=20;
> >
> > ch1->iir[0].B0=1;
> > ch1->iir[0].B1=0;
> > ch1->iir[0].B2=0;
> > ch1->iir[0].A1=0;
> > ch1->iir[0].A2=0;
> >
> > ch1->iir[1].B0=1;
> > ch1->iir[1].B1=0;
> > ch1->iir[1].B2=0;
> > ch1->iir[1].A1=0;
> > ch1->iir[1].A2=0;
> >
> > ch1->iir[2].B0=0.000769;
> > ch1->iir[2].B1=0.001538;
> > ch1->iir[2].B2=0.000769;
> > ch1->iir[2].A1=1.92076;
> > ch1->iir[2].A2=-0.923833;
> > EnableAxisDest(1,0);
> >
> > ch2->InputMode=NO_INPUT_MODE;
> > ch2->OutputMode=STEP_DIR_MODE;
> > ch2->Vel=40000;
> > ch2->Accel=200000;
> > ch2->Jerk=4e+006;
> > ch2->P=0;
> > ch2->I=0.01;
> > ch2->D=0;
> > ch2->FFAccel=0;
> > ch2->FFVel=0;
> > ch2->MaxI=200;
> > ch2->MaxErr=1e+006;
> > ch2->MaxOutput=200;
> > ch2->DeadBandGain=1;
> > ch2->DeadBandRange=0;
> > ch2->InputChan0=0;
> > ch2->InputChan1=0;
> > ch2->OutputChan0=10;
> > ch2->OutputChan1=0;
> > ch2->MasterAxis=-1;
> > ch2->LimitSwitchOptions=0x0;
> > ch2->InputGain0=1;
> > ch2->InputGain1=1;
> > ch2->InputOffset0=0;
> > ch2->InputOffset1=0;
> > ch2->OutputGain=-1;
> > ch2->OutputOffset=0;
> > ch2->SlaveGain=1;
> > ch2->BacklashMode=BACKLASH_OFF;
> > ch2->BacklashAmount=0;
> > ch2->BacklashRate=0;
> > ch2->invDistPerCycle=1;
> > ch2->Lead=0;
> > ch2->MaxFollowingError=1000000000;
> > ch2->StepperAmplitude=20;
> >
> > ch2->iir[0].B0=1;
> > ch2->iir[0].B1=0;
> > ch2->iir[0].B2=0;
> > ch2->iir[0].A1=0;
> > ch2->iir[0].A2=0;
> >
> > ch2->iir[1].B0=1;
> > ch2->iir[1].B1=0;
> > ch2->iir[1].B2=0;
> > ch2->iir[1].A1=0;
> > ch2->iir[1].A2=0;
> >
> > ch2->iir[2].B0=1;
> > ch2->iir[2].B1=0;
> > ch2->iir[2].B2=0;
> > ch2->iir[2].A1=0;
> > ch2->iir[2].A2=0;
> > EnableAxisDest(2,0);
> >
> > ch3->InputMode=NO_INPUT_MODE;
> > ch3->OutputMode=STEP_DIR_MODE;
> > ch3->Vel=40000;
> > ch3->Accel=200000;
> > ch3->Jerk=4e+006;
> > ch3->P=0;
> > ch3->I=0.01;
> > ch3->D=0;
> > ch3->FFAccel=0;
> > ch3->FFVel=0;
> > ch3->MaxI=200;
> > ch3->MaxErr=1e+006;
> > ch3->MaxOutput=200;
> > ch3->DeadBandGain=1;
> > ch3->DeadBandRange=0;
> > ch3->InputChan0=0;
> > ch3->InputChan1=0;
> > ch3->OutputChan0=11;
> > ch3->OutputChan1=0;
> > ch3->MasterAxis=-1;
> > ch3->LimitSwitchOptions=0x0;
> > ch3->InputGain0=1;
> > ch3->InputGain1=1;
> > ch3->InputOffset0=0;
> > ch3->InputOffset1=0;
> > ch3->OutputGain=-1;
> > ch3->OutputOffset=0;
> > ch3->SlaveGain=1;
> > ch3->BacklashMode=BACKLASH_OFF;
> > ch3->BacklashAmount=0;
> > ch3->BacklashRate=0;
> > ch3->invDistPerCycle=1;
> > ch3->Lead=0;
> > ch3->MaxFollowingError=1000000000;
> > ch3->StepperAmplitude=20;
> >
> > ch3->iir[0].B0=1;
> > ch3->iir[0].B1=0;
> > ch3->iir[0].B2=0;
> > ch3->iir[0].A1=0;
> > ch3->iir[0].A2=0;
> >
> > ch3->iir[1].B0=1;
> > ch3->iir[1].B1=0;
> > ch3->iir[1].B2=0;
> > ch3->iir[1].A1=0;
> > ch3->iir[1].A2=0;
> >
> > ch3->iir[2].B0=1;
> > ch3->iir[2].B1=0;
> > ch3->iir[2].B2=0;
> > ch3->iir[2].A1=0;
> > ch3->iir[2].A2=0;
> > EnableAxisDest(3,0);
> >
> >
> >
> > ch4->InputMode=NO_INPUT_MODE;
> > ch4->OutputMode=STEP_DIR_MODE;
> > ch4->Vel=40000;
> > ch4->Accel=200000;
> > ch4->Jerk=4e+006;
> > ch4->P=0;
> > ch4->I=0.01;
> > ch4->D=0;
> > ch4->FFAccel=0;
> > ch4->FFVel=0;
> > ch4->MaxI=200;
> > ch4->MaxErr=1e+006;
> > ch4->MaxOutput=200;
> > ch4->DeadBandGain=1;
> > ch4->DeadBandRange=0;
> > ch4->InputChan0=0;
> > ch4->InputChan1=0;
> > ch4->OutputChan0=14;
> > ch4->OutputChan1=0;
> > ch4->MasterAxis=-1;
> > ch4->LimitSwitchOptions=0x0;
> > ch4->InputGain0=1;
> > ch4->InputGain1=1;
> > ch4->InputOffset0=0;
> > ch4->InputOffset1=0;
> > ch4->OutputGain=-1;
> > ch4->OutputOffset=0;
> > ch4->SlaveGain=1;
> > ch4->BacklashMode=BACKLASH_OFF;
> > ch4->BacklashAmount=0;
> > ch4->BacklashRate=0;
> > ch4->invDistPerCycle=1;
> > ch4->Lead=0;
> > ch4->MaxFollowingError=1000000000;
> > ch4->StepperAmplitude=20;
> >
> > ch4->iir[0].B0=1;
> > ch4->iir[0].B1=0;
> > ch4->iir[0].B2=0;
> > ch4->iir[0].A1=0;
> > ch4->iir[0].A2=0;
> >
> > ch4->iir[1].B0=1;
> > ch4->iir[1].B1=0;
> > ch4->iir[1].B2=0;
> > ch4->iir[1].A1=0;
> > ch4->iir[1].A2=0;
> >
> > ch4->iir[2].B0=1;
> > ch4->iir[2].B1=0;
> > ch4->iir[2].B2=0;
> > ch4->iir[2].A1=0;
> > ch4->iir[2].A2=0;
> > EnableAxisDest(4,0);
> >
> >
> >
> > ch5->InputMode=NO_INPUT_MODE;
> > ch5->OutputMode=STEP_DIR_MODE;
> > ch5->Vel=40000;
> > ch5->Accel=200000;
> > ch5->Jerk=4e+006;
> > ch5->P=0;
> > ch5->I=0.01;
> > ch5->D=0;
> > ch5->FFAccel=0;
> > ch5->FFVel=0;
> > ch5->MaxI=200;
> > ch5->MaxErr=1e+006;
> > ch5->MaxOutput=200;
> > ch5->DeadBandGain=1;
> > ch5->DeadBandRange=0;
> > ch5->InputChan0=0;
> > ch5->InputChan1=0;
> > ch5->OutputChan0=15;
> > ch5->OutputChan1=0;
> > ch5->MasterAxis=-1;
> > ch5->LimitSwitchOptions=0x0;
> > ch5->InputGain0=1;
> > ch5->InputGain1=1;
> > ch5->InputOffset0=0;
> > ch5->InputOffset1=0;
> > ch5->OutputGain=-1;
> > ch5->OutputOffset=0;
> > ch5->SlaveGain=1;
> > ch5->BacklashMode=BACKLASH_OFF;
> > ch5->BacklashAmount=0;
> > ch5->BacklashRate=0;
> > ch5->invDistPerCycle=1;
> > ch5->Lead=0;
> > ch5->MaxFollowingError=1000000000;
> > ch5->StepperAmplitude=20;
> >
> > ch5->iir[0].B0=1;
> > ch5->iir[0].B1=0;
> > ch3->iir[0].B2=0;
> > ch5->iir[0].A1=0;
> > ch5->iir[0].A2=0;
> >
> > ch5->iir[1].B0=1;
> > ch5->iir[1].B1=0;
> > ch5->iir[1].B2=0;
> > ch5->iir[1].A1=0;
> > ch5->iir[1].A2=0;
> >
> > ch5->iir[2].B0=1;
> > ch5->iir[2].B1=0;
> > ch5->iir[2].B2=0;
> > ch5->iir[2].A1=0;
> > ch5->iir[2].A2=0;
> > EnableAxisDest(5,0);
> >
> >
> > DefineCoordSystem6(0,1,2,3,4,5);
> >
> > SetBitDirection(45,1); // set Enable Signal as Output
> > SetBit(45); // Enable the amplifiers
> >
> > // Add a small amount of Coordinated Motion Path smoothing if desired
> > // Tau = 0.001; // seconds for Low Pass Filter Time Constant
> > // KLP = exp(-TIMEBASE/Tau);
> > KLP=0; // force to 0 to disable
> > // printf("Tau=%f KLP=%f\n",Tau,KLP);
> >
> >
> > for (;;) // loop forever
> > {
> > WaitNextTimeSlice();
> >
> > // Service Amplifier disable after no activity for a while
> > if (ch0->Dest != LastX || ch1->Dest != LastY || ch2->Dest != LastZ)
> > {
> > // we moved - enable KStep Amplifers
> > SetBit(45);
> > T0 = Time_sec(); // record the time and position of last motion
> > LastX=ch0->Dest;
> > LastY=ch1->Dest;
> > LastZ=ch2->Dest;
> > }
> > else
> > {
> > if (Time_sec() > T0 + 10.0) ClearBit(45);
> > }
> > }
> >
> > return 0;
> > }
> >
> > --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> > >
> > > Hello Tom,
> > >
> > > I saw that to 'enable' the Kstep amp::
> > >
> > >
> > >
> > > From C code the Amplifiers may be enabled with the code shown below.
> > >
> > >
> > >
> > > SetBitDirection(45,1); // set Enable Signal as Output
> > >
> > > SetBit(45); // Enable the KStep Amplifiers
> > >
> > >
> > >
> > >
> > >
> > > Will this work for both ksteps?
> > >
> > >
> > > -Brad Murry
> > >
> > > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > > >
> > > > I see…. I misread and thought it was providing access to NO/NC
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Thanks Tom,
> > > >
> > > >
> > > >
> > > > -Brad
> > > >
> > > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of Tom Kerekes
> > > > Sent: Tuesday, February 07, 2012 3:31 PM
> > > > To: DynoMotion@yahoogroups.com
> > > > Subject: Re: [DynoMotion] Re: Double Ksteps
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi Brad,
> > > >
> > > >
> > > >
> > > > Flikering on bits 2 and 3 is normal. Thos are the multiplexing control bits going to KSTEP.
> > > >
> > > >
> > > >
> > > > USB power should be fine. In either case +12V is never required. Also take care Pin 4 of the Molex connector on KSTEP is the Stepper Motor power VBB. This is convienient for running Motors on +12V using a PC power supply. But take care not to feed +12V into the Molex and also some other voltage into the VBB screw terminals.
> > > >
> > > >
> > > >
> > > > No the relay outputs are basically like a completely isolated switch contact that will "close" when activated. So you wont see anything on the pins unless you source some current through it. The current will flow from the + to the - when energized.
> > > >
> > > >
> > > >
> > > > TK
> > > >
> > > >
> > > >
> > > > From: bradodarb <bradodarb@>
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Tuesday, February 7, 2012 2:20 PM
> > > > Subject: [DynoMotion] Re: Double Ksteps
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I am also seeing a lot of state flickering in bits 2-3.
> > > >
> > > > Is there a recommended grounding I should be doing here?
> > > >
> > > > I am only using USB power, should we be using the poer connector?
> > > >
> > > > If so, do we need to provide both 12v and 5v or can we just supply the 5v?
> > > >
> > > > Back to the relay outputs, should I be seeing kstep +bus voltage come out of pins 1 and 3 and -bus voltage on 2 and 4?
> > > >
> > > > In out case we out powering the ksteps with 24v, so that is what I should expect out of the relays?
> > > >
> > > > Thanks,
> > > >
> > > > Brad Murry
> > > >
> > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Tom Kerekes <tk@> wrote:
> > > > >
> > > > > They need to be configured a Outputs.
> > > > > ÃÆ'‚
> > > > > TK
> > > > >
> > > > > From: bradodarb <bradodarb@>
> > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > Sent: Tuesday, February 7, 2012 2:10 PM
> > > > > Subject: [DynoMotion] Re: Double Ksteps
> > > > >
> > > > >
> > > > > ÃÆ'‚
> > > > > Hello Tom,
> > > > >
> > > > > I seem to gave the isolated inputs working right after setting the Global var
> > > > >
> > > > > KStepPresent=TRUE;
> > > > >
> > > > > It seems to multiplex fine there.
> > > > >
> > > > > I cannot seem to get the relay outputs working though...
> > > > >
> > > > > From my understanding I should be able to set bits 0 and 1 in the digital IO screen of KMotion.exe and fire these relay outputs.
> > > > >
> > > > > Any thoughts?
> > > > >
> > > > > -Brad Murry
> > > > >
> > > > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> , Brad Murry <bradodarb@> wrote:
> > > > > >
> > > > > > Thanks Tom,
> > > > > >
> > > > > >
> > > > > >
> > > > > > I did see some mention here and there about using two cards regarding IO, etcÃÆ'Æ'¢ÃÆ'¢â€šÂ¬ÃÆ'‚¦ but was not sure if there were any other caveats.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Do I only need to set the FPGA command once on INIT?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> [mailto:DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ] On Behalf Of Tom Kerekes
> > > > > > Sent: Tuesday, February 07, 2012 11:52 AM
> > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > > Subject: Re: [DynoMotion] Double Ksteps
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi Brad,
> > > > > >
> > > > > >
> > > > > >
> > > > > > There is this:
> > > > > >
> > > > > >
> > > > > >
> > > > > > http://www.dynomotion.com/Help/SchematicsKStep/UsingKStep.htm
> > > > > >
> > > > > >
> > > > > >
> > > > > > But now that you mention it it needs a section on using two KSTEPS.
> > > > > >
> > > > > >
> > > > > >
> > > > > > The KSTEP with the 26 pin connector will be the first 4 axes (OutputChan 8-11)
> > > > > >
> > > > > > The KSTEP with the RH45 connecot will be the second 4 axes (OutputChan 12-15)
> > > > > >
> > > > > >
> > > > > >
> > > > > > (8 is added to select the TTL output mode that KSTEP requires rather than the open collector mode).
> > > > > >
> > > > > >
> > > > > >
> > > > > > BTW I just discovered that the step pulse needs to be inverted to have proper setup time for the Direction change. Currently the only way to do that is from C
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > FPGA(STEP_PULSE_LENGTH_ADD) = 0x80 + 32; // set inverted and to 2us
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > TK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > From: bradodarb <bradodarb@>
> > > > > > To: DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com>
> > > > > > Sent: Tuesday, February 7, 2012 10:42 AM
> > > > > > Subject: [DynoMotion] Double Ksteps
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hello Tom,
> > > > > >
> > > > > > I am not sure about the axis channel settings for use with the two Ksteps on our PLT machine. Are there some docs?
> > > > > >
> > > > > > -Brad Murry
> > > > > >
> > > > >
> > > >
> > >
> >
>